-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More detailed defaults for problem.get_full_vector
#1393
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## develop #1393 +/- ##
===========================================
+ Coverage 84.50% 84.52% +0.02%
===========================================
Files 157 157
Lines 12955 12958 +3
===========================================
+ Hits 10947 10953 +6
+ Misses 2008 2005 -3 ☔ View full report in Codecov by Sentry. |
…vor of lb_full and ub_full.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
Makes more sense for the default to grab problem.x_fixed_vals instead of not using them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! I left an optional suggestion to extend on the docstring.
Co-authored-by: Maren Philipps <55318391+m-philipps@users.noreply.github.com>
As the doctoring already explained before, we usually want
problem.x_fixed_vals
as defaults if we update a vector x. I think this should be a default and leaving the nans should be left for gradients (hence another parameter to distinguish the two.